Axiell Open Text image plugin

The Axiell WebAPI image server configuration

From wwwopac.ashx 3.7.15106.2 (.Net 4.5 required) an image plugin for the OpenText DAMS is available: OpenTextImagePlugin.dll. As all other plugins it allows you or your Axiell system (by means of retrieval paths for image fields) to communicate with the DAMS-specific API via the Axiell WebAPI. An appropriate configuration in adlibweb.xml is all you need to retrieve digital content via wwwopac.ashx queries. For OpenText you need a configuration similar to the following:

<imageServerConfiguration name="images">
   <servertype>FileSystem</servertype>
   <path></path>
   <cachePath>C:\Data\Model 4.2 SQL\imageCache</cachePath>
   <ImagePlugin type="Adlib.OpenText.Imaging.Plugin.OpenTextImagePlugin, OpenTextImagePlugin">
     <BaseUrl>http://76.495.082.83:28091/opentext</BaseUrl>
     <UserName>ouruser</UserName>
     <Password>q97m7dks857d4ng</Password>
     <Rendition>preview</Rendition>
   </ImagePlugin>
</imageServerConfiguration>

Each OpenText server will have its own BaseURL, UserName and Password (all mandatory parameters) so it depends on the customer utilizing an OpenText server how these parameters must be set. Rendition (optional) can be set to preview (which is the default setting) or thumbnail. This allows you to create different image server definitions for thumbnails and previews. A fictive example of a wwwopac.ashx request to an OpenText server:

http://damsservr/damsapi/wwwopac.ashx?command=getcontent&server=images&value=058c7ac3ff940ae6a1cd6dd860ce2a618f1b2dc0&width=300&height=300

Fix in 3.0.22013.1 for changes in OTMM

An update to OTMM (OpenText Media Management) caused a change in the OTMM metadata returned by the Axiell WebAPI plugin for OTMM to the WebAPI image server. The plugin was coded to look at the master_content node for previews, which is fine if the ingested master is a “known” type (has a recognizable mime-type extension). However, if a master came from tape, which uses an envelope format with an extension of .mxf, the plugin no longer recognized this format, and was going down the wrong route as a result. Since all assets that are viewable have a preview_content node, this node will now be used instead of the master_content node for the metadata crawl. Fixed in 3.0.22013.1.

Improvement of the configurability of renditions from version 3.0.21127.1

From version 3.0.21127.1, the adlibweb.xml configuration for this image plugin has an optional section in which to specify alternative renditions for specific content types. The list of Renditions can hold types Application, Video, Audio which relate to the type of content returned by OTMM. For PDFs the type is Application (from mimetype application/pdf). When no rendition exception is defined, the default rendition (as specified in the Rendition node directly underneath ImagePlugin) is still used as a fallback option. An example configuration looks like this:

  <imageServerConfiguration name="aispreviews">
    <defaultImage></defaultImage>
    <servertype>FileSystem</servertype>
    <imageOverlayFile>C:\Axiell\AIS IMAGEAPI\Image0032ShadowBG.png</imageOverlayFile>
    <imageOverlayBlend>65</imageOverlayBlend>
    <imageOverlayPosition>4</imageOverlayPosition>
    <imageOverlayPercentage>30</imageOverlayPercentage>
    <path></path>
    <cachePath>C:\Axiell\imageCache</cachePath>
    <ImagePlugin type="Adlib.OpenText.Imaging.Plugin.OpenTextImagePlugin, OpenTextImagePlugin">
      <BaseUrl>http://ourserver.edu/otmmapi/v4</BaseUrl>
      <UserName>axiellservice</UserName>
      <Password>0p3jk89d7t</Password>
      <Rendition>preview</Rendition>
      <Renditions>
        <Rendition Type="Application">thumbnail</Rendition>
      </Renditions>
    </ImagePlugin>
    <ignoreScaleVideo>true</ignoreScaleVideo>
  </imageServerConfiguration>

So here the default rendition is preview and the exception for Application type content is thumbnail.